Archive Utility Unable to expand

Question

Level 1

10 points

Archive Utility Unable to expand

Problem: Whenever a user tries to open a .zip file, Archive Utility throws the following error:

Unable to finish expanding "<name of .zip>" into "<folder name>". Could not move "<name of unzipped file/folder>" into destination directory.

Environment:

Mac OS X 10.7.5

Network Home Folders (on a RAID attached to 10.7.5 Server)

~/Library/Caches redirected to /tmp/<username>

Already Tried:

Local user - No Problem Found

Current Network User - Problem

New Network User - Problem

Removed ~/Library/Preferences/com.apple.archiveutility.plist & repairpermissions (as suggested in other threads) - no difference

Turning off ~/Library/Caches redirection - no difference

Thoughts: Permissions/sandboxing? Though I don't see how. Permissions all show as correct. No other problems with files copying/being created, just expanding .zip files. Expanding to local storage (e.g. /Users/Shared) works fine.

Logging seems to be non-existant so I have no decent information on which to go. Is there a hidden defaults write I can use to enable a debugging menu like with Disk Utility?

Thanks.

~W

Posted on Oct 3, 2013 7:09 AM

Reply

Answer 1

Apr 6, 2017 1:51 PM in response to woodgie

I know this is an old question but I just experenced this with a user running 10.12.4 using SMB to connect to a Windows 2008R2 server cluster. This works fine on a Windows 2003R2 server (spun it up to test this). This seems to be yet another issue with SMB on Macs. I changed the protocol to CIFS and it expands successfully now on the 2008R2 server cluster. Under Connect to Server, change the servername from smb://<server> to cifs://<server> You may not see smb:// but if a protocol isn't explicitedly typed, Mac will assume SMB. So just add cifs:// in from of the servername, cifs://<server>

P.S. I've also noticed that using uppercase SMB:// when connecting to a server share for the fiist time, it will sometimes fail. I now always use lowercase smb://

I

Reply

Answer 2

woodgie Author

Level 1

10 points

Jan 20, 2014 9:16 AM in response to woodgie

I'm still experiencing this and no closer to working out what's happening. Does anyone have any thoughts?

~W

Reply

Answer 3

mazzeppa

Level 1

4 points

Apr 22, 2015 2:19 PM in response to woodgie

We have the same problem on our NetApp servers that we access via SMB. This problem started for us when we upgraded to Mac OS 10.9, and still have the problem with Mac OS 10.10.3. It does work fine when uncompressing a zip file that contains only a single file. It is when we are uncompressing a folder where we see the problem. On the other hand, we CAN uncompress the same troubled zipped file (that contains a folder) on the same server using the "unzip" terminal command. So it's only in the Mac GUI (Finder) that we have this problem.

Still no solution that I no of.

...Ron

Reply

Answer 4

Jan 22, 2016 2:05 AM in response to woodgie

Did either of you solve this? I think I have the same issue. I've also found that when a user tries to expand a zip archive on our Win Server 2012 SMB share, they not only get the same error you report but it leaves behind a empty folder with a randomly generated name like .BAH.Xj6S5. This folder cannot be read or deleted without changing its ownership and permissions on the server.

Reply